home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.20021006-20030409
/
000346_jrd@cc.usu.edu_Sat Mar 1 15:19:03 EST 2003.msg
< prev
next >
Wrap
Text File
|
2020-01-01
|
3KB
|
48 lines
Article: 14143 of comp.protocols.kermit.misc
Path: newsmaster.cc.columbia.edu!panix!newsfeed.media.kyoto-u.ac.jp!newsfeed.icl.net!newsfeed.fjserv.net!news.maxwell.syr.edu!xmission!news.cc.utah.edu!cc.usu.edu!jrd
From: jrd@cc.usu.edu (Joe Doupnik)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: MS-DOS Kermit
Message-ID: <smJqS8E+f8CK@cc.usu.edu>
Date: 1 Mar 03 12:32:02 MDT
References: <20030301.1833.31585snz@aral.vorkosigan.co.uk>
Organization: Utah State University
Lines: 35
Xref: newsmaster.cc.columbia.edu comp.protocols.kermit.misc:14143
In article <20030301.1833.31585snz@aral.vorkosigan.co.uk>, mike@aral.vorkosigan.co.uk (Michael Bernardi) writes:
> Given that many servers no longer support telnet and instead use ssh,
> is there any chance that the MS-DOS version of kermit might be updated
> to use this protocol as well? MS-Kermit is the best dos terminal
> emulation program around and I'd like to use it to manage my linux
> server. But for security considerations it doesn't (and will not be
> modified) allow telnet access, so I can;t :-(
>
> It seems a shame that the only platforms that seem to be developed now
> are C-Kermit and Kermit for Windows32, and that other systems have be
> let fallow.
> Mike
-----------------
There is a bit of ANSI terminal emulation on MSK. There is a lack
of information here as to just what ANSI or SCO ANSI <etc> actually contain
in detail. Also I don't have an SCO machine to be a local reference. A
formal reference is really required with terminal emulation development.
As a matter of annoyance, the VIM editor commonly found on Linux
has horrible terminal emulation handling, and I have pushed it off a cliff
in favor of a passible edition of vi.
On SSH. That's a rather large can of wiggly things. MSK has no
crypto support, the laws on export have been difficult for everyone. And,
to be candid here, my readings of SSH source code a couple of years ago
caused me to shun the item completely on Unix systems. Maybe I overreacted
and need an education. In any case, memory space is at a premium with MSK
so whatever is done needs to be quite small and uncomplicated and to always
yield a usable connection even if the other side proves difficult.
On my gear there is a sprinkling of SSL stuff for web work, no SSH,
no r* utilities, and no paranoia about wire snoops. Keeping certificates
straight is enough bother, and openssl isn't very nice about that.
Guidance and views on the above items are certainly welcomed. I
don't mean to appear reactionary on these matters, but also I don't believe
95% of the claims folks advance for crypto features. Old simple XOR-ing
probably does as well to keep away casual packet snoopers.
Joe D.